← Home

@tmlmobilidade/emails

25
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

joaovasconcelosjusimen

Keywords

public transittmltransportes metropolitanos de lisboaservices

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern rapid-publish AI (publish-pattern): 815 versions with date-stamped versioning indicates automated CI/CD; rapid publish is expected behavior for this package. ai
phantom-deps phantom-dep:browserslist AI (phantom-deps): browserslist is a build-time config dep, not directly imported in source. ai
phantom-deps phantom-dep:@types/nodemailer AI (phantom-deps): Type-only package loaded by TypeScript convention, not directly imported. ai
dependencies unvetted-dep:@tmlmobilidade/dates AI (dependencies): Same-org internal dependency; consistent pattern across all @tmlmobilidade/* packages. ai
provenance no-provenance AI (provenance): No provenance across this org's packages; stable false positive for this publisher. ai
npm-metadata no-description AI (npm-metadata): Intentional internal package; missing description is consistent across the org's packages. ai
phantom-deps phantom-dep:react-email AI (phantom-deps): react-email is a declared runtime dep used as a dev/CLI tool; phantom detection is a false positive for this package. ai

Versions (showing 25 of 25)

Version Deps Published
20260604.2309.43 6 / 7
20260525.1830.15 6 / 7
20260525.1615.59 6 / 7
20260525.1614.32 6 / 7
20260518.901.35 6 / 7
20260518.827.12 6 / 7
20260507.2220.24 6 / 7
20260507.1757.50 6 / 7
20260504.1217.59 6 / 7
20260429.1713.40 7 / 7
20260418.1237.24 7 / 7
20260410.1133.41 8 / 6
20260409.1552.16 8 / 6
20260331.1620.53 8 / 6
20260329.1522.22 8 / 6
20260326.2207.53 8 / 6
20260326.1644.50 8 / 6
20260326.219.51 8 / 6
20260324.1220.16 8 / 6
20260323.400.54 8 / 6
20260316.1439.45 8 / 6
20260225.1312.4 10 / 6
20260222.2136.56 10 / 6
20260216.1613.20 10 / 6
20260130.1104.56 10 / 6

v20260604.2309.43

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20260525.1830.15

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1615.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260525.1614.32

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.901.35

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260518.827.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260507.2220.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260507.1757.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260504.1217.59

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260429.1713.40

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260418.1237.24

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260410.1133.41

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260409.1552.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260331.1620.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260329.1522.22

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260326.2207.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260326.1644.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260326.219.51

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260324.1220.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260323.400.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260316.1439.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260225.1312.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260222.2136.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260216.1613.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v20260130.1104.56

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.